Providing automatic dependent surveillance - broadcast data for unmanned aerial vehicles

ABSTRACT

A device can be configured to receive flight data from an unmanned aerial vehicle (UAV), where the flight data indicates at least one of an identifier that identifies the UAV, a location of the UAV, an altitude of the UAV, a bearing of the UAV, or a speed of the UAV. The device can be further configured to convert at least a portion of the flight data from a first format to a second format; generate automatic dependent surveillance-broadcast (ADS-B) data based on the converted flight data; and perform an action associated with the ADS-B data.

RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.15/652,151, entitled “PROVIDING AUTOMATIC DEPENDENTSURVEILLANCE-BROADCAST DATA FOR UNMANNED AERIAL VEHICLES”, filed Jul.17, 2017, which is incorporated herein by reference.

BACKGROUND

Automatic dependent surveillance-broadcast (ADS-B) is a surveillancetechnology in which an aircraft determines its position via satellitenavigation and periodically broadcasts its position, enabling theaircraft to be tracked. ADS-B information can be received by air trafficcontrol ground stations as a replacement for secondary surveillanceradar (SSR). ADS-B data can also be received by some aircraft to providesituational awareness and allow for collision avoidance.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram of an overview of an example implementationdescribed herein;

FIG. 2 is a diagram of an example environment in which systems and/ormethods, described herein, can be implemented;

FIG. 3 is a diagram of example components of one or more devices of FIG.2;

FIG. 4 is a flow chart of an example process for providing automaticdependent surveillance-broadcast data for unmanned aerial vehicles;

FIG. 5 is a diagram of an example implementation relating to the exampleprocess shown in FIG. 4; and

FIG. 6 is a diagram of an example implementation relating to the exampleprocess shown in FIG. 4.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The following detailed description of example implementations refers tothe accompanying drawings. The same reference numbers in differentdrawings can identify the same or similar elements.

While air traffic control stations and some aircraft are able to tracknearby aircraft using technologies such as ADS-B and SSR, unmannedaerial vehicles (UAVs) can pose a risk in certain airspaces. UAVs arefrequently flown for many different purposes and in many differentareas, they are not typically equipped with ADS-B equipment, and theycan be difficult to detect using SSR (e.g., due to the relatively smallsize of many UAVs and the lower altitudes at which UAVs are oftenflown). The inability for air traffic control stations and aircraft toreliably track UAVs can, in some situations, pose risk to air safety.

Some implementations, described herein, provide an ADS-B gateway toreceive flight data from a UAV, generate ADS-B data based on the flightdata, and provide the ADS-B data for receipt by air traffic controlstations and/or aircraft. For example, the ADS-B gateway can receive,from a UAV or a device in communication with the UAV, UAV flight data(e.g., UAV flight data can be provided to the ADS-B gateway via a radioaccess network (RAN) such as a long-term evolution (LTE) network). UAVflight data can include a variety of information related to the UAV,such as a UAV identifier, UAV location, UAV altitude, UAV speed, and/orthe like. Based on the received UAV flight data, the ADS-B gateway cangenerate ADS-B data. For example, the ADS-B gateway can identify, fromflight data received from the UAV, flight data that is relevant to ADS-Band generate an ADS-B message that includes the relevant flight dataformatted for ADS-B technology.

In some implementations, the ADS-B gateway can provide an ADS-B message,which includes UAV flight data formatted for ADS-B, for broadcast toaircraft that can use the UAV flight data included in the ADS-B messageto identify and/or track the UAV. In some implementations, the ADS-Bgateway can provide ADS-B data to an air traffic control station (e.g.,via an internet protocol (IP) based network or the like), enabling theair traffic control station to identify and/or track the UAV and/orbroadcast the ADS-B data to aircraft. In some implementations, the ADS-Bgateway can provide an ADS-B message to an aircraft using a wireless IPnetwork, such as an LTE network. For example, in some implementations,aircraft can be equipped with an LTE device capable of receiving ADS-Bdata via LTE and providing the ADS-B data to an ADS-B device of theaircraft.

In some implementations, the ADS-B gateway can facilitate the provisionof aircraft ADS-B data to a UAV. For example, ADS-B gateway can receive,from an air traffic control device, an ADS-B message indicating thelocation, speed, and altitude of an aircraft. In this example, the ADS-Bgateway can generate aircraft data for providing a UAV with data thatthe UAV can use to identify and/or track the aircraft. For example, theADS-B gateway can generate aircraft data by identifying the relevantflight information included in the ADS-B message, formatting therelevant flight information in a manner capable of being interpreted bythe UAV, and send formatted aircraft data to the UAV (e.g., via an LTEnetwork or the like).

Some implementations described herein can enable an air traffic controldevice to provide aircraft, such as commercial, industrial, and militaryairplanes and helicopters, with ADS-B messages that facilitate UAVidentification and tracking by the aircraft. This can allow aircraft,which might otherwise be unaware of their proximity to one or more UAVs,to have improved situational awareness and enable collision avoidancemethods to account for UAVs operating in proximate airspace. Improvedsituational awareness of the location of UAVs, by air trafficcontrollers and/or aircraft, can improve the safety of aircraft flights,including UAV flights. In addition, the ability to provide UAVs withaircraft data indicating the location of proximate aircraft, can furtherimprove safety by providing a UAV with situational awareness, whichmight improve collision avoidance techniques used by the UAV.

By using ADS-B messages, air traffic control stations and/or aircraftcan avoid the need to obtain new or upgraded equipment, as an ADS-Bgateway can provide UAV flight data in a format readable by existingADS-B devices. This can reduce the cost of flight safety relative toother options that might require additional or upgraded technology to beequipped by aircraft and/or air traffic controllers. In someimplementation, the security of the ADS-B system, can be improved byusing IP-based networks to provide UAV flight data to aircraft ratherthan relying on ADS-B broadcasts, which might be spoofed (e.g., in asituation where an aircraft is equipped with an IP device capable ofreceiving ADS-B messages over IP and providing the ADS-B messages to anADS-B device of the aircraft).

FIG. 1 is a diagram of an overview of an example implementation 100described herein. As shown in FIG. 1, example implementation 100 caninclude a UAV in communication with an ADS-B gateway via RAN, and an airtraffic control device in communication with an aircraft via ADS-Btransmitter.

As shown in FIG. 1, and by reference number 110, the UAV can provideflight data to the ADS-B gateway over a RAN, such as an LTE network orthe like. For example, various components of the UAV can collect flightdata, such as the UAV location from a global positioning satellite (GPS)component, UAV altitude from an altimeter component, and UAV speed fromUAV airspeed indicator component. The flight data can be transmitted tothe ADS-B gateway using a transmitter component of the UAV, such as anLTE modem or other component capable of transmitting flight data over aRAN.

As further shown in FIG. 1, and by reference number 120, the ADS-Bgateway generates ADS-B data based on the flight data received from theUAV. In some implementations, the ADS-B gateway can extract the flightdata from an IP-based network packet and format the flight data forinclusion in an ADS-B message. This can include, for example, convertingthe UAV location, altitude, speed, and/or other flight data into a56-bit ADS message string. In some implementations, the ADS-B gatewaycan identify a Mode Select (Mode S) address, or identifier, for the UAV,and include the Mode S address in the ADS-B data. A Mode S address is anaircraft identifier, and the Mode S address for the UAV can beidentified by the ADS-B gateway in a variety of ways (e.g., the Mode Saddress could be provided by the UAV, provided by an entity that ownsthe UAV, or predetermined based on one or more features of the UAV). Insome implementations, the ADS-B gateway can generate an ADS-B messagefrom the flight data. For example, the ADS-B gateway can, using theflight data provided by the UAV, generate a 112-bit ADS-B message thatincludes the Mode S address associated with the UAV and the ADS datathat includes the latitude, longitude, altitude, and velocity of theUAV.

As further shown in FIG. 1, and by reference number 130, the ADS-Bgateway provides the ADS-B data to the air traffic control device. Insome implementations, the ADS-B data is provided to the air trafficcontrol device via a network, such as an IP-based wired or wirelessnetwork. For example, the ADS-B gateway can encapsulate an ADS-B messagein an IP packet and transmit the IP packet to the air traffic controldevice via a network, such as the Internet. In some implementations, theADS-B gateway and air traffic control device are collocated (e.g.,obviating the use of a network to provide ADS-B data to air trafficcontrol device).

As further shown in FIG. 1, and by reference number 140, the ADS-B datathat includes the UAV location, altitude, and speed, is provided to anaircraft. In some implementations, the ADS-B data can be provided to theaircraft via an ADS-B transmitter. In this example, an ADS-B deviceincluded in the aircraft can receive the ADS-B message and use the datato identify and locate the UAV. In some implementations, ADS-B data canbe provided to the aircraft in other ways. For example, ADS-B data canbe transmitted to the aircraft using an IP-based network, such as an LTEnetwork, and an IP-based device included in the aircraft can provide theADS-B data to other systems of the aircraft, such as an ADS-B device. Asanother example, an air traffic controller can use the air trafficcontrol device to identify and track the UAV from the provided ADS-Bdata, and the air traffic controller can then use radio communicationsto inform a pilot of the aircraft regarding the UAVs position.

In some implementations, the ADS-B gateway can provide aircraft data,such as the aircraft location, altitude, and speed, to the UAV or apilot of the UAV. For example, an ADS-B device included in the aircraftcan broadcast an ADS-B message that includes the aircrafts location,altitude, and speed. The broadcast can be received by the air trafficcontrol device, which can provide that ADS-B message to the ADS-Bgateway. The ADS-B gateway can then generate an IP-based message forconveying the aircraft data to the UAV and/or to a device being used topilot the UAV. The IP-based message that includes the aircraft data canthen be transmitted to the UAV and/or UAV pilot device via an IP-basednetwork, such as an LTE network, providing situational awareness to theUAV and/or UAV pilot.

Accordingly, the example implementation 100 depicts an ADS-B gatewaydevice that can increase flight safety and efficiency for both mannedand unmanned flights. For example, flight safety can be improved byproviding air traffic control, aircraft, UAVs, and/or theircorresponding operators, with situational awareness regarding aircraftand/or UAVs that might be in close proximity to one another. Thesituational awareness can enable aircraft and/or UAVs to avoid potentialcollisions (e.g., using collision avoidance technology and/or manualcontrol). Flight efficiency can be improved, for example, by providingaircraft and air traffic controllers with a relatively accurateawareness of the aircraft operating in a given airspace, which canenable more precise and/or economical air traffic patterns to be safelyused by the aircraft.

As indicated above, FIG. 1 is provided merely as an example. Otherexamples are possible and can differ from what was described with regardto FIG. 1.

FIG. 2 is a diagram of an example environment 200 in which systemsand/or methods, described herein, can be implemented. As shown in FIG.2, environment 200 can include a mobile device 205; a base station 210;a mobility management entity device (MME) 215; a serving gateway (SGW)220; a packet data network gateway (PGW) 225; a home subscriber server(HSS) 230; an authentication, authorization, and accounting server (AAA)235; an ADS-B Gateway 240; a network 250; and air traffic control device260. Devices of environment 200 can interconnect via wired connections,wireless connections, or a combination of wired and wirelessconnections.

Some implementations are described herein as being performed within along term evolution (LTE) network for explanatory purposes. Someimplementations can be performed within a network that is not an LTEnetwork, such as a third generation (3G) network, or another type ofwireless network.

Environment 200 can include an evolved packet system (EPS) that includesan LTE network and/or an evolved packet core (EPC) that operate based ona third generation partnership project (3GPP) wireless communicationstandard. The LTE network can include a radio access network (RAN) thatincludes one or more base stations 210 that take the form of evolvedNode Bs (eNBs) via which mobile device 205 communicates with the EPC.The EPC can include MME 215, SGW 220, PGW 225, and/or ADS-B gateway 240that enable mobile device 205 to communicate with network 250 and/or anInternet protocol (IP) multimedia subsystem (IMS) core. The IMS core caninclude HSS 230 and/or AAA 235, and can manage device registration andauthentication, session initiation, etc., associated with mobile devices205. HSS 230 and/or AAA 235 can reside in the EPC and/or the IMS core.

Mobile device 205 includes one or more devices capable of communicatingwith base station 210 and/or a network (e.g., network 250). For example,mobile device 205 can include a wireless communication device, aradiotelephone, a personal communications system (PCS) terminal (e.g.,that can combine a cellular radiotelephone with data processing and datacommunications capabilities), a smart phone, a laptop computer, a tabletcomputer, a personal gaming system, and/or a similar device. In someimplementations, a mobile device 205 can include a UAV or a device usedto pilot the UAV, or mobile device 205 can be included in the UAV,enabling the UAV and/or the device used to pilot the UAV to communicatewith base station 210 and/or network 250. Mobile device 205 can sendtraffic to and/or receive traffic from network 250 (e.g., via basestation 210, SGW 220, PGW 225 and/or ADS-B gateway 240).

Base station 210 includes one or more devices capable of transferringtraffic, such as audio, video, text, and/or other traffic, destined forand/or received from mobile device 205. In some implementations, basestation 210 can include an eNB associated with the LTE network thatreceives traffic from and/or sends traffic to network 250 via SGW 220and/or PGW 225. Additionally, or alternatively, one or more basestations 210 can be associated with a RAN that is not associated withthe LTE network. Base station 210 can send traffic to and/or receivetraffic from mobile device 205 via an air interface. In someimplementations, base station 210 can include a small cell base station,such as a base station of a microcell, a picocell, and/or a femtocell.

MME 215 includes one or more devices, such as one or more serverdevices, capable of managing authentication, activation, deactivation,and/or mobility functions associated with mobile device 205. In someimplementations, MME 215 can perform operations relating toauthentication of mobile device 205. Additionally, or alternatively, MME215 can facilitate the selection of a particular SGW 220 and/or aparticular PGW 225 to serve traffic to and/or from mobile device 205.MME 215 can perform operations associated with handing off mobile device205 from a first base station 210 to a second base station 210 whenmobile device 205 is transitioning from a first cell associated with thefirst base station 210 to a second cell associated with the second basestation 210. Additionally, or alternatively, MME 215 can select anotherMME (not pictured), to which mobile device 205 should be handed off(e.g., when mobile device 205 moves out of range of MME 215).

SGW 220 includes one or more devices capable of routing packets. Forexample, SGW 220 can include one or more data processing and/or traffictransfer devices, such as a gateway, a router, a modem, a switch, afirewall, a network interface card (NIC), a hub, a bridge, a serverdevice, an optical add/drop multiplexer (OADM), or any other type ofdevice that processes and/or transfers traffic. In some implementations,SGW 220 can aggregate traffic received from one or more base stations210 associated with the LTE network, and can send the aggregated trafficto network 250 (e.g., via PGW 225) and/or other network devicesassociated with the EPC and/or the IMS core. SGW 220 can also receivetraffic from network 250 and/or other network devices, and can send thereceived traffic to mobile device 205 via base station 210.Additionally, or alternatively, SGW 220 can perform operationsassociated with handing off mobile device 205 to and/or from an LTEnetwork.

PGW 225 includes one or more devices capable of providing connectivityfor mobile device 205 to external packet data networks (e.g., other thanthe depicted EPC and/or LTE network). For example, PGW 225 can includeone or more data processing and/or traffic transfer devices, such as agateway, a router, a modem, a switch, a firewall, a NIC, a hub, abridge, a server device, an OADM, or any other type of device thatprocesses and/or transfers traffic. In some implementations, PGW 225 canaggregate traffic received from one or more SGWs 220, and can send theaggregated traffic to network 250. Additionally, or alternatively, PGW225 can receive traffic from network 250, and can send the traffic tomobile device 205 via SGW 220 and base station 210. PGW 225 can recorddata usage information (e.g., byte usage), and can provide the datausage information to AAA 235.

HSS 230 includes one or more devices, such as one or more serverdevices, capable of managing (e.g., receiving, generating, storing,processing, and/or providing) information associated with mobile device205. For example, HSS 230 can manage subscription information associatedwith mobile device 205, such as information that identifies a subscriberprofile of a user associated with mobile device 205, information thatidentifies services and/or applications that are accessible to mobiledevice 205, location information associated with mobile device 205, anetwork identifier (e.g., a network address) that identifies mobiledevice 205, information that identifies a treatment of mobile device 205(e.g., quality of service information, a quantity of minutes allowed pertime period, a quantity of data consumption allowed per time period,etc.), and/or similar information. HSS 230 can provide this informationto one or more other devices of environment 200 to support theoperations performed by those devices.

AAA 235 includes one or more devices, such as one or more serverdevices, that perform authentication, authorization, and/or accountingoperations for communication sessions associated with mobile device 205.For example, AAA 235 can perform authentication operations for mobiledevice 205 and/or a user of mobile device 205 (e.g., using one or morecredentials), can control access, by mobile device 205, to a serviceand/or an application (e.g., based on one or more restrictions, such astime-of-day restrictions, location restrictions, single or multipleaccess restrictions, read/write restrictions, etc.), can track resourcesconsumed by mobile device 205 (e.g., a quantity of voice minutesconsumed, a quantity of data consumed, etc.), and/or can perform similaroperations.

ADS-B gateway 240 includes one or more devices, such as one or moreserver devices, capable of receiving flight data from a mobile device205 and/or air traffic control device 260, generating flight data basedon the received flight data, and/or providing mobile device 205 and/orair traffic control device 260 with flight data. For example, ADS-Bgateway 240 can receive one or more IP packet(s) from mobile device 205,extract UAV flight data from the IP packet(s), generate an ADS-B messageusing the extracted UAV flight data, including formatting the flightdata for ADS-B, and provide the ADS-B message to air traffic controldevice 260 (e.g., by encapsulating the ADS-B message in an IP packet andtransmitting the packet to air traffic control device 260 via network250). Flight data received and/or transmitted by ADS-B gateway 240 can,in some implementations, be supported by one or more other devices ofenvironment 200.

Network 250 includes one or more wired and/or wireless networks. Forexample, network 250 can include a cellular network (e.g., an LTEnetwork, a 3G network, a code division multiple access (CDMA) network,etc.), a public land mobile network (PLMN), a wireless local areanetwork (e.g., a Wi-Fi network), a local area network (LAN), a wide areanetwork (WAN), a metropolitan area network (MAN), a telephone network(e.g., the Public Switched Telephone Network (PSTN)), a private network,an ad hoc network, an intranet, the Internet, a fiber optic-basednetwork, a cloud computing network, and/or a combination of these orother types of networks.

Air traffic control device 260 includes one or more devices, such as oneor more server devices, capable of receiving and/or providing ADS-B dataassociated with a UAV or other aircraft. In some implementations, airtraffic control device 260 can receive, from ADS-B gateway 240, ADS-Bdata regarding a UAV that includes a mobile device 205. Air trafficcontrol device 260 can provide the ADS-B data regarding the UAV, forexample, to a user or an aircraft and/or the like (e.g., air trafficcontrol device 260 can include a display for displaying ADS-B data to auser of air traffic control device, or air traffic control device 260can use an ADS-B broadcast antenna to broadcast ADS-B data regarding theUAV to an ADS-B device on an aircraft. In some implementations, ADS-Bdata received and/or provided by air traffic control device 260 can beformatted in a manner suitable for an ADS-B system (e.g., a formatsuitable for transmission via very high frequency (VHF) (Data link mode2 or 4), 1090 Extended Squitter (1090ES), 978 megahertz Universal AccessTransceiver (UAT), and/or the like). For example, some ADS-Bimplementations may communicate using pairs of 112-bit messagestransmitted using 1090ES technology. In some implementations, airtraffic control device 260 can provide, to ADS-B gateway 240, ADS-B dataregarding an aircraft. ADS-B data received and/or transmitted by airtraffic control device 260 can, in some implementations, be supported byone or more other devices of environment 200.

The number and arrangement of devices and networks shown in FIG. 2 areprovided as an example. In practice, there can be additional devicesand/or networks, fewer devices and/or networks, different devices and/ornetworks, or differently arranged devices and/or networks than thoseshown in FIG. 2. Furthermore, two or more devices shown in FIG. 2 can beimplemented within a single device, or a single device shown in FIG. 2can be implemented as multiple, distributed devices. Additionally, oralternatively, a set of devices (e.g., one or more devices) ofenvironment 200 can perform one or more functions described as beingperformed by another set of devices of environment 200.

FIG. 3 is a diagram of example components of a device 300. Device 300can correspond to mobile device 205, base station 210, MME 215, SGW 220,PGW 225, HSS 230, AAA 235, ADS-B Gateway 240, and/or air traffic controldevice 260. In some implementations, mobile device 205, base station210, MME 215, SGW 220, PGW 225, HSS 230, AAA 235, ADS-B Gateway 240,network 250 and/or air traffic control device 260 can include one ormore devices 300 and/or one or more components of device 300. As shownin FIG. 3, device 300 can include a bus 310, a processor 320, a memory330, a storage component 340, an input component 350, an outputcomponent 360, and a communication interface 370.

Bus 310 includes a component that permits communication among thecomponents of device 300. Processor 320 is implemented in hardware,firmware, or a combination of hardware and software. Processor 320 is acentral processing unit (CPU), a graphics processing unit (GPU), anaccelerated processing unit (APU), a microprocessor, a microcontroller,a digital signal processor (DSP), a field-programmable gate array(FPGA), an application-specific integrated circuit (ASIC), or anothertype of processing component. In some implementations, processor 320includes one or more processors capable of being programmed to perform afunction. Memory 330 includes a random access memory (RAM), a read onlymemory (ROM), and/or another type of dynamic or static storage device(e.g., a flash memory, a magnetic memory, and/or an optical memory) thatstores information and/or instructions for use by processor 320.

Storage component 340 stores information and/or software related to theoperation and use of device 300. For example, storage component 340 caninclude a hard disk (e.g., a magnetic disk, an optical disk, amagneto-optic disk, and/or a solid state disk), a compact disc (CD), adigital versatile disc (DVD), a floppy disk, a cartridge, a magnetictape, and/or another type of non-transitory computer-readable medium,along with a corresponding drive.

Input component 350 includes a component that permits device 300 toreceive information, such as via user input (e.g., a touch screendisplay, a keyboard, a keypad, a mouse, a button, a switch, and/or amicrophone). Additionally, or alternatively, input component 350 caninclude a sensor for sensing information (e.g., a global positioningsystem (GPS) component, an accelerometer, a gyroscope, and/or anactuator). Output component 360 includes a component that providesoutput information from device 300 (e.g., a display, a speaker, and/orone or more light-emitting diodes (LEDs)).

Communication interface 370 includes a transceiver-like component (e.g.,a transceiver and/or a separate receiver and transmitter) that enablesdevice 300 to communicate with other devices, such as via a wiredconnection, a wireless connection, or a combination of wired andwireless connections. Communication interface 370 can permit device 300to receive information from another device and/or provide information toanother device. For example, communication interface 370 can include anEthernet interface, an optical interface, a coaxial interface, aninfrared interface, a radio frequency (RF) interface, a universal serialbus (USB) interface, a Wi-Fi interface, a cellular network interface,and/or the like.

Device 300 can perform one or more processes described herein. Device300 can perform these processes based on processor 320 executingsoftware instructions stored by a non-transitory computer-readablemedium, such as memory 330 and/or storage component 340. Acomputer-readable medium is defined herein as a non-transitory memorydevice. A memory device includes memory space within a single physicalstorage device or memory space spread across multiple physical storagedevices.

Software instructions can be read into memory 330 and/or storagecomponent 340 from another computer-readable medium or from anotherdevice via communication interface 370. When executed, softwareinstructions stored in memory 330 and/or storage component 340 can causeprocessor 320 to perform one or more processes described herein.Additionally, or alternatively, hardwired circuitry can be used in placeof or in combination with software instructions to perform one or moreprocesses described herein. Thus, implementations described herein arenot limited to any specific combination of hardware circuitry andsoftware.

The number and arrangement of components shown in FIG. 3 are provided asan example. In practice, device 300 can include additional components,fewer components, different components, or differently arrangedcomponents than those shown in FIG. 3. Additionally, or alternatively, aset of components (e.g., one or more components) of device 300 canperform one or more functions described as being performed by anotherset of components of device 300.

FIG. 4 is a flow chart of an example process 400 for providing ADS-Bdata for UAVs. In some implementations, one or more process blocks ofFIG. 4 can be performed by ADS-B Gateway 240. In some implementations,one or more process blocks of FIG. 4 can be performed by another deviceor a group of devices separate from or including ADS-B Gateway 240, suchas mobile device 205, base station 210, MME 215, SGW 220, PGW 225, HSS230, AAA 235, network 250, and/or air traffic control device 260.

As shown in FIG. 4, process 400 can include receiving flight data froman aircraft (block 410). For example, ADS-B gateway 240 can receiveflight data from mobile device 205, which can be included in or incommunication with an aircraft, such as a UAV. By way of an exampleregarding a UAV, a cell phone used to pilot the UAV and/or acommunications device included in or otherwise in communication with theUAV, can obtain flight data, such as a UAV identifier, UAV location, UAValtitude, UAV bearing, and/or UAV speed, from a variety of sources,including UAV sensors and/or other device(s) used to track the UAV. TheUAV flight data obtained by mobile device 205 can be transmitted toADS-B gateway 240 via network 250 (e.g., in one or more IP packetstransmitted to ADS-B gateway 240 using an LTE network or other type ofIP-based network).

The flight data received by ADS-B gateway 240 can be expressed in avariety of ways. For example, a UAV identifier can include a UAV modelnumber, an owner of the UAV, an organization in control of the UAV,and/or the like. UAV location can include a street address, a city, astate, GPS data, and/or the like. UAV altitude can include a barometricaltitude measurement, a GPS altitude measurement, and/or the like. UAVbearing can include an absolute bearing, a relative bearing, a waypoint,and/or the like. UAV speed can include a ground speed measurement, anair speed measurement, a GPS speed measurement, and/or the like. Otherflight data related to the UAV can also be expressed in a variety ofways.

In this way, ADS-B gateway 240 can receive flight data from a UAV,enabling ADS-B gateway 240 to generate an ADS-B message.

As further shown in FIG. 4, process 400 can include generating ADS-Bdata based on the flight data (block 420). For example, ADS-B gateway240 can generate an ADS-B message using the flight data provided by theUAV. In some implementations, ADS-B gateway 240 converts one or moreportions of the flight data to a format suitable for the ADS-B system(e.g., a format suitable for transmission via very high frequency (VHF)(Data link mode 2 or 4), 1090 Extended Squitter (1090ES), 978 megahertzUniversal Access Transceiver (UAT), and/or the like). For example, theADS-B gateway 240 can receive flight data regarding the UAV in one ormore IP packets, and each portion of the received flight data can beformatted in a way not suitable for transmission via ADS-B. In thissituation, ADS-B gateway 240 can format one or more pieces of the flightdata in a manner suitable for the ADS-B system and generate one or moreADS-B messages that include the formatted flight data.

By way of example, UAV location data provided by a UAV can include GPScoordinates and/or National Marine Electronics Association (NMEA) 0183data that specifies the location of the UAV in a particular format, suchas degrees, minutes, and seconds, degrees and decimal minutes, and/ordecimal degrees. In some implementations, an ADS-B message can specifylocation using a 17-bit latitude and 17-bit longitude (e.g., expressedin binary, octal, hexadecimal, or decimal format). In this situation,ADS-B gateway 240 can convert the UAV location data provided by the UAVto a 17-bit latitude and 17-bit longitude suitable for inclusion in anADS-B message.

As another example, UAV altitude data provided by a UAV can include aGPS altitude measurement provided in NMEA 0183 format. In someimplementations, an ADS-B message can specify altitude using 12 bits(e.g., expressed in binary, octal, hexadecimal, or decimal format). Inthis situation, ADS-B gateway 240 can convert the UAV altitude dataprovided by the UAV to a 12-bit altitude measurement suitable forinclusion in an ADS-B message.

As yet another example, UAV bearing data provided by a UAV can include awaypoint that specifies a geographic location to which the UAV isheaded. In some implementations, an ADS-B message can specify bearingusing 22 bits of an ADS message (e.g., expressed in binary, octal,hexadecimal, or decimal format). In this situation, ADS-B gateway 240can calculate a bearing using a current location of the UAV relative tothe waypoint location, and convert the result into a 22-bit stringspecifying a bearing measurement suitable for inclusion in an ADS-Bmessage.

As a further example, UAV speed data provided by a UAV can include ameasurement in miles per hour or the like. In some implementations, anADS-B message can specify a ground speed measurement in knots using 10bits (e.g., expressed in binary, octal, hexadecimal, or decimal format).In this situation, ADS-B gateway 240 can convert the UAV speed dataprovided by the UAV to a 10-bit speed measurement suitable for inclusionin an ADS-B message.

In some implementations, ADS-B gateway 240 can determine, based on theflight data, an identifier to include in an ADS-B message. For example,an example ADS-B message can include 24 bits that can be used toidentify an aircraft (e.g., using a Mode Select (Mode S) address or thelike, such as a Mode S address provided by the International CivilAviation Organization). In some implementations, each UAV can beassociated with a unique identifier suitable for inclusion in an ADS-Bmessage, such as a 24-bit Mode S address. In this situation, ADS-Bgateway 240 can identify the Mode S address associated with the UAV fromwhich the flight data was provided, and include the Mode S address in anADS-B message. For example, the UAV can include the Mode S address inthe flight data provided to ADS-B gateway 240, or ADS-B gateway 240 canobtain a Mode S address for the UAV using the flight data. For example,the flight data provided by the UAV can include a UAV identifier, whichADS-B gateway can look up in a database or other data storage device tolocate a corresponding Mode S address.

In some implementations, multiple UAVs can be associated with one Mode Saddress. Given the relatively large number of UAVs that can be activelyflying at any given time, providing a unique 24-bit Mode S address toeach of them, while retaining uniqueness for other aircraft identifiedby 24-bit Mode S addresses, might be impractical. Multiple UAVs can beassociated with one Mode S address, for example, to enableidentification of UAVs in general, or certain types of UAVs. Forexample, all UAVs can be associated with one Mode S address. As anotherexample, all UAVs belonging to a particular organization can beassociated with the same Mode S address, enabling distinction to be madebetween UAVs of different organizations. As a further example, UAVs canbe classified by size and/or weight, and each UAV in a given class ofUAV can be associated with the same Mode S address as other UAVs in thatgiven class.

The foregoing example message formatting details for ADS-B messages aremerely examples, and many other different types of ADS-B messages, orADS-B message formatting techniques, can be used to generate an ADS-Bmessage. In some implementations, ADS-B gateway 240 can generatedifferent types of ADS-B messages for the UAV flight data. For example,ADS-B gateway 240 can generate one ADS-B message that specifies alocation and altitude of a UAV, and another ADS-B message that specifiesa speed and heading of the UAV. In some implementations, ADS-B gateway240 can generate ADS-B messages in multiple formats. For example, ADS-Bgateway 240 can generate, based on UAV flight data, an ADS-B message ina first format for a first air traffic controller and another ADS-Bmessage in a second format for a second air traffic controller.

In this way, ADS-B gateway 240 can generate an ADS-B message based onflight data regarding a UAV. The ability to generate ADS-B data for UAVaircraft can enable ADS-B gateway 240 to perform a variety of actionsassociated with the ADS-B data, including actions that facilitateaircraft collision avoidance and promote situational awareness.

As further shown in FIG. 4, process 400 can include performing an actionassociated with the ADS-B data (block 430). For example, ADS-B gateway240 can perform a variety of actions associated with the ADS-B data. Insome implementations, ADS-B gateway 240 provides the ADS-B data to airtraffic control device 260. For example, ADS-B gateway 240 canencapsulate one or more ADS-B messages in an IP packet and transmit thatpacket to air traffic control device 260 via network 250. As anotherexample, ADS-B gateway 240 and air traffic control device 260 can becollocated (e.g., included in the same device and/or in directcommunication with one another through a non-network-based interface),obviating the use of network 250 to communicate ADS-B data between ADS-Bgateway 240 and air traffic control device 260.

In some implementations, ADS-B gateway 240 can cause the ADS-B data tobe broadcast by an ADS-B broadcast device. For example, ADS-B gateway240 can provide ADS-B data to an ADS-B broadcast antenna, directly orindirectly (e.g., via air traffic control device 260) for transmissionto one or more aircraft.

In some implementations, ADS-B gateway 240 can cause the ADS-B data tobe provided to a device operating on an aircraft using IP-based networktechnology. For example, an aircraft can be equipped with a separatedevice similar to mobile device 205, which can be capable of receivingIP-based network communications, such as LTE communications. In thissituation, ADS-B gateway 240 can cause transmission of the ADS-B data tothe device included in the aircraft via LTE, enabling the deviceincluded in the aircraft to provide the ADS-B data to equipment of theaircraft, such as ADS-B equipment and/or collision avoidance equipmentincluded in the aircraft.

In some implementations, ADS-B gateway 240 can store and/or keep a logof ADS-B data and/or associated UAV flight data. The storage and/orlogging of ADS-B data and/or associated UAV flight data can facilitate avariety of functions, such as investigation and analytics functionsdesigned to improve the safety and/or efficiency of UAV and otheraircraft flights.

In some implementations, ADS-B gateway 240 can provide a notificationbased on the ADS-B data. For example, ADS-B data can be provided to anowner/operator of the UAV, enabling the owner/operator of the UAV to usethe ADS-B data for a variety of purposes, such as record keeping oranalytics. In some implementations, ADS-B data can be provided to anauthority, such as a flight safety organization or law enforcementagency. In this situation, ADS-B data can provide situational awarenessto authorities that, similar to air traffic controllers that can beoperating air traffic control device 260, might be capable of preventingpotential problems.

In this way, ADS-B gateway 240 can perform an action associated with theADS-B data. The action(s) taken (e.g., providing ADS-B messages to airtraffic controllers and/or aircraft), can be designed to facilitate safeand efficient operation of an aircraft and/or UAV.

Although FIG. 4 shows example blocks of process 400, in someimplementations, process 400 can include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 4. Additionally, or alternatively, two or more of theblocks of process 400 can be performed in parallel.

For example, in some implementations, ADS-B gateway 240 can receiveADS-B data and generate data that can be provided to a UAV and/or mobiledevice 205 associated with the UAV. In this situation, ADS-B gateway 240can use techniques similar to those discussed above, to provide aircraftflight data to the UAV and/or UAV pilot. Providing aircraft data to aUAV and/or UAV pilot from ADS-B aircraft data can improve situationalawareness of the UAV and UAV pilot (e.g., enabling the UAV and/or UAVpilot to take action designed to avoid a collision with the aircraftassociated with the ADS-B aircraft data).

FIG. 5 is a diagram of an example implementation 500 relating to exampleprocess 400 shown in FIG. 4. FIG. 5 shows an example of providing ADS-Bdata for UAVs.

As shown in FIG. 5, ADS-B gateway 240 can convert an example Internetprotocol version 4 (IPv4) network packet 510 into an example ADS-Bmessage 520. As indicated by the example implementation 500, the examplepacket 510 can include a header that includes 20-32 bytes of data toenable proper handling of the packet 510 (e.g., identifying packetprotocol, packet destination, and/or the like). The example packet 510also includes up to 65,503 bytes for a payload. In some implementations,an example packet 510 could include all of the UAV flight data to beconverted by ADS-B gateway. For example, the payload can include a UAVidentifier, UAV location, UAV bearing, and UAV speed.

As also indicated by the example implementation 500, the example ADS-Bmessage 520 can include 8 bits for control, 24 bits for a Mode S address(e.g., a unique aircraft identifier), 56 bits for an ADS message (e.g.,such as latitude, longitude, bearing, and/or speed), and 24 bits forparity. In some implementations, ADS-B gateway 240 can identify UAVflight data included in the IPv4 packet 510, convert the flight data toa format suitable for the ADS-B messaging system, and generate an ADS-Bmessage 520, or messages, that include(s) the converted flight data.ADS-B gateway 240 can perform an action based on the ADS-B message 520,such as causing transmission of the ADS-B message 520 by an ADS-Btransmitter.

As indicated above, FIG. 5 are provided merely as an example. Otherexamples are possible and can differ from what was described with regardto FIG. 5.

FIG. 6 is a diagram of an example implementation 600 relating to exampleprocess 400 shown in FIG. 4. FIG. 6 shows an example of ADS-B gateway240 providing aircraft flight data to a UAV and/or device associatedwith a UAV.

As shown in FIG. 6, and by reference number 610, an aircraft broadcastsADS-B data to air traffic control device 260. The ADS-B data can includea variety of flight data for the aircraft, such as an aircraftidentifier, aircraft location, aircraft altitude, and aircraft speed.

As further shown in FIG. 6, and by reference number 620, air trafficcontrol device 260 provides the ADS-B data to ADS-B gateway 240. Forexample, air traffic control device 260 can encapsulate ADS-B data in anIP network packet and transmit it to ADS-B gateway 240 via network 250.

As further shown in FIG. 6, and by reference number 630, ADS-B gateway240 generates aircraft flight data based on the ADS-B data. For example,in a manner similar to the conversion of UAV flight data to ADS-B data,ADS-B gateway can convert ADS-B data to aircraft flight data that isformatted in a manner suitable for interpretation and/or handling by aUAV and/or a device associated with the UAV.

As further shown in FIG. 6, and by reference number 640, ADS-B gateway240 performs an action associated with the aircraft flight data. In thisexample, ADS-B gateway 240 causes transmission of the aircraft flightdata to the UAV, e.g., via an IP-based network such as an LTE network.

As indicated above, FIG. 6 are provided merely as an example. Otherexamples are possible and can differ from what was described with regardto FIG. 6.

Some implementations of ADS-B gateway 240 described herein can improvesafety and efficiency of all manner of aircraft flights, including UAVs.For example, ADS-B messages that identify UAVs to aircraft and flightcontrollers can provide aircraft pilots and air traffic controllers withsituational awareness regarding UAVs in airspace that might pose ahazard to the aircraft. Improving situational awareness can, forexample, improve navigation and collision avoidance systems. Inimplementations where aircraft are equipped with devices capable ofreceiving IP-based transmissions, the security of ADS-B messaging can beimproved, e.g., by providing ADS-B data by specific addressingtechniques rather than relying on broadcasts that could be spoofed.

The foregoing disclosure provides illustration and description, but isnot intended to be exhaustive or to limit the implementations to theprecise form disclosed. Modifications and variations are possible inlight of the above disclosure or can be acquired from practice of theimplementations.

As used herein, the term component is intended to be broadly construedas hardware, firmware, or a combination of hardware and software.

To the extent the aforementioned embodiments collect, store, or employpersonal information provided by individuals, it should be understoodthat such information shall be used in accordance with all applicablelaws concerning protection of personal information. Additionally, thecollection, storage, and use of such information can be subject toconsent of the individual to such activity, for example, through wellknown “opt-in” or “opt-out” processes as can be appropriate for thesituation and type of information. Storage and use of personalinformation can be in an appropriately secure manner reflective of thetype of information, for example, through various encryption andanonymization techniques for particularly sensitive information.

It will be apparent that systems and/or methods, described herein, canbe implemented in different forms of hardware, firmware, or acombination of hardware and software. The actual specialized controlhardware or software code used to implement these systems and/or methodsis not limiting of the implementations. Thus, the operation and behaviorof the systems and/or methods were described herein without reference tospecific software code—it being understood that software and hardwarecan be designed to implement the systems and/or methods based on thedescription herein.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of possible implementations. In fact,many of these features can be combined in ways not specifically recitedin the claims and/or disclosed in the specification. Although eachdependent claim listed below can directly depend on only one claim, thedisclosure of possible implementations includes each dependent claim incombination with every other claim in the claim set.

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems, and can be used interchangeably with “one or more.” Furthermore,as used herein, the term “set” is intended to include one or more items(e.g., related items, unrelated items, a combination of related andunrelated items, etc.), and can be used interchangeably with “one ormore.” Where only one item is intended, the term “one” or similarlanguage is used. Also, as used herein, the terms “has,” “have,”“having,” or the like are intended to be open-ended terms. Further, thephrase “based on” is intended to mean “based, at least in part, on”unless explicitly stated otherwise.

What is claimed is:
 1. A method, comprising: receiving, by a device,flight data for an unmanned aerial vehicle (UAV), the flight dataindicating a location of the UAV, and the flight data further indicatingat least one of: an identifier that identifies the UAV, an altitude ofthe UAV, a bearing of the UAV, or a speed of the UAV; converting, by thedevice, the location of the UAV from a first format to an automaticdependent surveillance-broadcast (ADS-B) format, wherein the firstformat comprises: a global positioning satellite (GPS) coordinateformat, and a National Marine Electronics Association (NMEA) format;generating, by the device, ADS-B data based on the converted location ofthe UAV; and performing, by the device, an action associated with theADS-B data.
 2. The method of claim 1, wherein the flight data indicatesthe identifier that identifies the UAV, and wherein the method furthercomprises: determining a Mode select (Mode S) identifier for the UAVbased on the identifier that identifies the UAV, the Mode S identifieridentifying at least one of: an operator of the UAV, or a type of theUAV.
 3. The method of claim 2, wherein determining the Mode S identifiercomprises: determining the Mode S identifier by performing a lookup, ina data storage device and using the identifier that identifies the UAV,to identify an association between the identifier that identifies theUAV and the Mode S identifier.
 4. The method of claim 2, whereingenerating ADS-B data comprises: generating an ADS-B message thatspecifies the Mode S identifier; and wherein performing the actioncomprises: transmitting the ADS-B message.
 5. The method of claim 2,wherein the Mode S identifier is associated with a plurality of UAVs,each of the plurality of UAVs sharing the at least one of: the operatorof the UAV, or the type of the UAV.
 6. The method of claim 1, whereinperforming the action comprises: causing an ADS-B broadcast antenna tobroadcast at least a portion of the ADS-B data.
 7. The method of claim1, wherein performing the action comprises: encapsulating at least aportion of the ADS-B data in an internet protocol packet; andtransmitting the internet protocol packet.
 8. A device, comprising: oneor more memories; and one or more processors, communicatively coupled tothe one or more memories, configured to: receive flight data from anunmanned aerial vehicle (UAV), the flight data indicating: a location ofthe UAV, an identifier that identifies the UAV, and at least one of: analtitude of the UAV, a bearing of the UAV, or a speed of the UAV;convert the location of the UAV from a first format to an automaticdependent surveillance-broadcast (ADS-B) format, wherein the firstformat comprises: a global positioning satellite (GPS) coordinateformat, and a National Marine Electronics Association (NMEA) format; andgenerate ADS-B data based on the converted location of the UAV and basedon the identifier that identifies the UAV; and perform an actionassociated with the ADS-B data.
 9. The device of claim 8, wherein theone or more processors are further configured to: determine a Modeselect (Mode S) identifier for the UAV based on the identifier thatidentifies the UAV, the Mode S identifier identifying at least one of:an operator of the UAV, or a type of the UAV.
 10. The device of claim 9,wherein the one or more processors, when determining the Mode Sidentifier, are configured to: determine the Mode S identifier byperforming a lookup, in a data storage device and using the identifierthat identifies the UAV, to identify an association between theidentifier that identifies the UAV and the Mode S identifier.
 11. Thedevice of claim 9, wherein the one or more processors, when generatingADS-B data, are configured to: generate an ADS-B message that specifiesthe Mode S identifier; and wherein the one or more processors, whenperforming the action, are configured to: transmit the ADS-B message.12. The device of claim 9, wherein the Mode S identifier is associatedwith a plurality of UAVs, each of the plurality of UAVs sharing the atleast one of: the operator of the UAV, or the type of the UAV.
 13. Thedevice of claim 8, wherein the one or more processors, when performingthe action, are configured to: cause an AD S-B broadcast antenna tobroadcast at least a portion of the ADS-B data.
 14. The device of claim8, wherein the one or more processors, when performing the action, areconfigured to: encapsulate at least a portion of the ADS-B data in aninternet protocol packet; and cause transmission of the internetprotocol packet.
 15. A non-transitory computer-readable medium storing aset of instructions, the set of instructions comprising: one or moreinstructions that, when executed by one or more processors of a device,cause the device to: receive flight data for an unmanned aerial vehicle(UAV), the flight data indicating a location of the UAV, and the flightdata further indicating at least one of: an identifier that identifiesthe UAV, an altitude of the UAV, a bearing of the UAV, or a speed of theUAV; convert the location of the UAV from a first format to an automaticdependent surveillance-broadcast (ADS-B) format, wherein the firstformat comprises: a global positioning satellite (GPS) coordinateformat, and a National Marine Electronics Association (NMEA) format;generate ADS-B data based on the converted location of the UAV;encapsulate at least a portion of the ADS-B data in an internet protocolpacket; and cause transmission of the internet protocol packet.
 16. Thenon-transitory computer-readable medium of claim 15, wherein the flightdata indicates the identifier that identifies the UAV, and wherein theone or more instructions further cause the device to: determine a Modeselect (Mode S) identifier for the UAV based on the identifier thatidentifies the UAV, the Mode S identifier identifying at least one of:an operator of the UAV, or a type of the UAV.
 17. The non-transitorycomputer-readable medium of claim 16, wherein the one or moreinstructions, that cause the device to determine the Mode S identifier,cause the device to: determine the Mode S identifier by performing alookup, in a data storage device and using the identifier thatidentifies the UAV, to identify an association between the identifierthat identifies the UAV and the Mode S identifier.
 18. Thenon-transitory computer-readable medium of claim 16, wherein the one ormore instructions, that cause the device to generate ADS-B data, causethe device to: generate an ADS-B message that specifies the Mode Sidentifier; and wherein the one or more instructions, that cause thedevice to encapsulate at least the portion of the ADS-B data in theinternet protocol packet, cause the device to: encapsulate the ADS-Bmessage in the internet protocol packet.
 19. The non-transitorycomputer-readable medium of claim 16, wherein the Mode S identifier isassociated with a plurality of UAVs, each of the plurality of UAVssharing the at least one of: the operator of the UAV, or the type of theUAV.
 20. The non-transitory computer-readable medium of claim 15,wherein the one or more instructions further cause the device to: causean ADS-B broadcast antenna to broadcast the portion of the ADS-B data.